Skip to main content

This is a new service – your feedback will help us to improve it.

Calderdale Metropolitan Borough Council

Tree preservation zone

There is a problem

  • 564 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

Land off Norcliffe Lane, Hipperholme.

reference
94/00854/C
name
Land off Norcliffe Lane, Hipperholme.
tree-preservation-order

undefined

94/00854/C
tree-preservation-zone-type
woodland
geometry
MULTIPOLYGON (((-1.823537 53.723302,-1.823452 53.723296,-1.823402 53.723296,-1.823128 53.723312,-1.823061 53.723308,-1.822993 53.723301,-1.822951 53.723291,-1.822906 53.723283,-1.822874 53.723270,-1.822851 53.723258,-1.822808 53.723283,-1.822763 53.723301,-1.822696 53.723332,-1.822626 53.723370,-1.822568 53.723397,-1.822498 53.723439,-1.822433 53.723473,-1.822367 53.723502,-1.822340 53.723516,-1.822311 53.723527,-1.822238 53.723560,-1.822200 53.723574,-1.822161 53.723586,-1.822038 53.723621,-1.821982 53.723633,-1.821912 53.723646,-1.821858 53.723654,-1.821831 53.723660,-1.821882 53.723699,-1.821902 53.723711,-1.821933 53.723736,-1.821968 53.723767,-1.821992 53.723792,-1.822003 53.723808,-1.822185 53.723756,-1.822344 53.723714,-1.822425 53.723690,-1.822460 53.723678,-1.822550 53.723653,-1.822578 53.723643,-1.822616 53.723632,-1.822650 53.723618,-1.822678 53.723610,-1.822959 53.723515,-1.823064 53.723482,-1.823153 53.723446,-1.823188 53.723427,-1.823258 53.723396,-1.823370 53.723353,-1.823438 53.723335,-1.823504 53.723324,-1.823546 53.723315,-1.823549 53.723312,-1.823549 53.723309,-1.823546 53.723306,-1.823537 53.723302)))
point
POINT (-1.822627 53.723512)
notes
Beech, sycamore, willow
entry-date
1994-08-26
start-date
1994-08-26
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Calderdale Metropolitan Borough Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL